Method and system for providing a networked collaborative work environment

ABSTRACT

A system and method for providing a collaborative work environment includes servers and client workstations. Client workstations receive data objects from one or more servers and combine the received data objects with stored templates to render HTML pages representing at least a portion of a common project. Users may view, edit, and create common documents for the projects and upload them to the server using a drag-and-drop interface. Additionally, since all file transfers take place using HTTP, project groups can span corporate organizations as well as time zones and geographic boundaries.

FIELD OF THE INVENTION

The present invention relates to networked systems and, moreparticularly, to systems and methods for providing a collaborative workenvironment over a network.

BACKGROUND OF THE INVENTION

The world wide network of computers commonly known as the “Internet” hasgrown rapidly over the last several years. Much of this growth has beendriven by the increase in popularity of the World Wide Web (“WWW” or“Web”). The WWW is a collection of files written using HyperText MarkupLanguage (HTML), commonly referred to as “Web pages.” HTML files may beeasily configured and created by users and accessed and displayed usingspecialized applications known as Web browsers, which allow a user toaccess and view HTML files using a graphical user interface.

Servers hosting HTML files can communicate using the HyperText TransferProtocol (“HTTP”). HTTP is a communication protocol that provides useraccess to files (which can be in different formats such as text,graphics, images, sound, video, etc.) written using the HTML pagedescription language. HTML provides basic document formatting functionsand allows the developer of the HTML page to specify communication linksto other servers and files. Use of an HTML-compliant browser on a clientworkstation involves specification of a link via a Uniform ResourceLocator address or “URL”. Upon such specification, the browser makes a“TCP/IP” request to the server address identified by the link andreceives a Web page in return. The browser executing on the clientworkstation interprets the HTML file that it has received and displaysthe Web page to the user of the client workstation.

The browser renders the Web page by interpreting HTML tags, which areembedded control information that indicates to a browser when certainaction should be taken. For example, a tag may indicate to the browser:(1) that a graphics file should be retrieved and displayed at aparticular location on the screen; (2) that the text following the HTMLtag should be centered, bolded, or otherwise formatted; (3) that thebackground of the Web page should be shaded or have a particularpattern; or (4) that a different HTML file should be loaded anddisplayed in place of the HTML the file the browser in currentlydisplaying.

The relative ease with which information may be collected, organized,and displayed to users throughout the world has made HTML files apopular way of disseminating information in a networked environment. Forexample, a broad range of companies now use internal collections of HTMLfiles, which are commonly known as “Intranets.” However, while HTMLfiles excel at displaying and disseminating information to one or moregroups of networked users, they do not allow a group of users tocollaboratively share information in order to work on a common project.For example, although a collection of HTML files may allow separateusers to publish information for consumption by one or more othermembers of a project team, such a collection of files does not does notfacilitate a two-way exchange of information and project data betweenteam members. For example, a team member viewing another team member'sHTML file cannot add new comments or files to the file being viewed.

SUMMARY OF THE INVENTION

The present invention relates to methods and systems for providing anetworked, collaborative work environment. In particular, the systemsand methods described below allow a group of users to share work andfiles, engage in discussions related to a common project, and otherwisecollaborate. For example, users interact with Web browsers executing ontheir client workstations to access Web pages that allow them to:participate in ongoing discussions; create new discussions about projecttopics; upload files to a common area associated with the Web page;download files and edit files that have been uploaded to the Web page byothers members of the project team; and create new pages of varioustypes and link them to existing ones. Thus, the disclosed systems andmethods allow a set of geographically or corporately separate users toparticipate on a common project. In addition, the systems and methods ofthe present invention allow one or more of the users that are authorizedto use the set of Web pages representing the common project to enableother users to access the Web page, that is, to allow those users to addnew members to the team.

In one aspect, the present invention relates to a method for locallygenerating HTML pages for display which includes the steps of: receivingdata associated with a project via a network; storing the receivedproject data in a database; retrieving an HTML file from a memoryelement; and using the stored, received data in conjunction with theretrieved HTML file to render an HTML page for display to the user of aclient workstation. In some embodiments, the databases areODBC-compliant.

In another aspect, the invention relates to a system for allowing userto collaborate on a shared project using an HTML file server. A projectdatabase is stored on the HTML file server and contains informationrelated to the shared project. Each client workstation locally stores asubset database which includes information related to the project whichis relevant to that user's effort on the project. A plurality of HTMLfiles is used in connection with the stored project information torender HTML pages for display to the user.

In still another aspect, the present invention relates to a method forproviding a collaborative workspace which allows users to perform workon a shared project. A file request is received from a clientworkstation. An application capable of viewing the file is invoked. Ifthe file was modified then it is transmitted to the server. In someembodiments, the modified file is transmitted using HTTP.

In still another aspect, the present invention relates to a method fortransmitting files from a client workstation executing a network browserto a server which includes the steps of selecting a file to betransferred and dragging the selected file onto the browser application.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is pointed out with particularity in the appended claims.The advantages of the invention described above, as well as furtheradvantages of the invention, may be better understood by reference tothe following description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1. is a block diagram of a system for providing a collaborativework environment;

FIG. 2 is a diagrammatic view of a facility as stored by a serverdatabase;

FIG. 3 is a diagrammatic view of a client workstation that may be usedin the system of FIG. 1;

FIG. 4 is a screen shot of an HTML page viewed by a user of the systemof FIG. 1;

FIG. 5 is a flowchart of the steps taken by a client workstation torender an HTML page of the sort depicted in FIG. 4;

FIG. 6 is a flowchart of the steps taken by a client workstation toallow users of the system to edit files;

FIG. 7 is a flowchart of the steps taken by the client workstation toallow users of the system to upload files to a server using a“drag-and-drop” interface; and

FIG. 8 is a flowchart of the steps taken by the system to transfer afile using HTTP.

DETAILED DESCRIPTION OF THE INVENTION

Referring now to FIG. 1, and in brief overview, a system for providing acollaborative work environment via a network is shown. Clientworkstations 12′ are connected to one or more servers 14. The clientworkstations 12′ may be connected in any physical arrangement such as astar, loop, ring, or bus. The network connecting client workstations 12′and the server 14 may use any physical media, including wireless,provided that the physical media supports the HyperText TransferProtocol (HTTP).

The server 14 stores information relating to a project or a set ofprojects, referred to as a facility, in a database 20 which may be aflat database, relational database, multi-dimensional database, orobject-oriented database. Each server 14 may store more than onedatabase 20, where each database 20 represents a different facility. Forexample, one server may host project facilities for separate researchefforts within one organization or for separate research efforts byseparate organizations. Each facility is viewed by a user as a directoryof eRoom pages. Referring now to FIG. 2, a directory of eRooms 22 asstored in the server database 20 is shown. Each entry provides at leastone link to an eRoom front page 24, which in turn may contain othereRoom pages 27, folders containing database objects 28 or files 29.

Databases 20 may be stored by the server 14 on any convenient massstorage device. For example, FIG. 1 depicts an embodiment in which theserver 14 stores the database 20 on an associated hard disk drive 16.Alternatively, the server 14 may store the database in Random AccessMemory (RAM) if the database 20 is capable of fitting within thephysical memory space of the server 14. The server 14 responds torequests for portions of the database 20 made by the client workstations12′ and transfers the requested data objects over the network to therequesting client workstation 12′.

The server database 20 stores various tables which contain informationabout eRooms, members, access controls, and other data objects. Forexample, a members table may be provided which includes uniqueidentification codes for each user, a table value indicating for whicheRooms the user fulfills a coordinator role, a table value whichindicates for which eRooms the member fulfills an observer role, and avalue describing the last time the member record was modified.Similarly, an eRooms table may be provided which includes a globallyunique handle identifying the eRoom and one or more room flags whichindicate various room attributes, such as whether a coordinator cancreate an eRoom, or whether the eRoom is a temporary, or trial, eRoom.Objects may also be represented by a table which includes as fieldsidentification codes for each data object, one or more flags which areused to distinguish various objects, one or more flags which are used todetermine the behavior of objects (editability, searchability, andothers), a field indicating the date the object was created, a fieldindicating who created the object, a field identifying the parent of theobject, and a field identifying the date the object was last modified,among others.

Referring also to FIG. 3, The client workstation 12′ may be any machinethat supports reception and transmission of data signals over an HTTPnetwork. In general, a client workstation 12′ is a personal computerexecuting a “browser” program to display an HTML page 40, on the screen30 of the client workstation 12′. The user interacts with pagesdisplayed by the browser utilizing a “point-and-click” interface, i.e.,the viewing user uses a mouse 32 to manipulate a cursor 42 that is alsodisplayed on the screen 30 of the client workstation 12′. Once thecursor 42 is over a particular portion of the HTML page 40, the viewinguser signals by “clicking” or “double clicking” a button 33 on the mouse32. Alternatively, the viewing user may also signal by pressing a key onan associated keyboard 36, such as the “return” key. In otherembodiments, the viewing user may not use a mouse 32 at all, but mayinstead use a touchpad, a trackball, a pressure-sensitive tablet andpen, or any other input mechanism for manipulating the cursor.

The client workstation 12′ uses a local database 20′ to store dataobjects related to a project, while external files related to a project(such as a word processing document of a set of meeting minutes) arestored in the client workstation's 12′ local file system. The clientdatabase 20′ may be provided as a flat file database, relationaldatabase, multi-dimensional database, or object-oriented database. Forexample, a typical relational database that may be used to provide aclient database 20′ is Jet Database Engine, manufactured by MicrosoftCorporation of Redmond, Wash. The database 20′ stored on the clientworkstation 12′ contains a relevant subset of the data objects stored bythe server 14. That is, the database 20 stored by the server 14typically will contain more information about a particular project thanthe database 20′ stored by the client workstation 12′.

However, the database 20′ stored on the client workstation 12′ maycontain tables which are not stored by the server database 20. Forexample, a client workstation 12 may store in its database an “unread”table which indicates which objects have been modified since the user ofthe client workstation 12′ has last accessed those objects. An unreadtable may include a member identification field and a modification tagindicating the last modification date and time of an object. All recordsmay be read from this table to identify to the client workstation 12′every item in a particular eRoom page which has not been read by theuser, or a selective database query may be done to return only thoseobjects belonging to a particular set of eRoom pages that have not beenread by the user. If it is desired to provide this functionality, anadditional entry in the unread table must be made to allow data objectsto be distinguished based on some indication of affiliation.

Certain important information, such as hierarchy and navigationinformation, related to the project database 20 is considered “skeleton”information. Skeleton information is a set of database records thatcontain basic properties needed to display Web pages representing theproject and therefore client workstations 12′ require frequent updatesof this information. Accordingly, it is generally desirable to excludelarge information from skeleton information associated with a project,such as notes relating to an ongoing discussion, to facilitatetransmission of the skeleton information to client workstations 12′.

The client workstation 12′ uses project data received from the server 14in combination with one or more template files to create and display tothe user of the client workstation a private, secure collection of HTMLpages that provide a virtual workroom for members of a team, whateverits size and wherever the members of the team are physically orcorporately located, may be referred to throughout as an “eRoom”, or an“eRoom page”. An eRoom is a set of connected HTML pages displayed to auser that displays project-related files, data, and discussion lists.Members of a team may congregate, share work and files, discuss ideas,stay informed and otherwise collaborate on common projects using aneRoom.

Client workstations 12′ generally have local memory elements for storingdata objects of files associated with a project that are downloaded fromthe server 14 as well as one or more eRoom templates. A clientworkstation 12′ may have an associated mass storage device such as ahard disk drive 16′ or a tape drive 18′ for storing the set of eRoomtemplates, although if a client workstation 12′ is provided with enoughRAM to store the set of eRoom templates, then the mass storage devicesneed not be provided.

FIG. 4 depicts an embodiment of an eRoom page 60 that a user mightencounter while using a popular “browser” program, Internet Explorer,manufactured by Microsoft Corporation of Redmond, Wash. The eRoom pagehas five major elements: a page element 402; a navigation bar 404; agraphical identifier 406; an item box 408; and a shortcut list 410.

The page element 402 may include subelements. In the embodiment depictedin FIG. 4, a discussion 420 is embedded within the page and there is afacility 422 to allow a viewer to contribute to the discussion 420. Theembedded discussion 420 and the contribution facility 422 may beimplemented as ActiveX controls, a JAVA applet, or various other means.Further, the facility name is displayed 424, as is the name of theviewed page 426 and a description of the viewed page 428.

The navigation bar 404 provides a number of controls for the viewer ofthe page. For example, in the page embodiment shown in FIG. 4, thenavigation bar 404 provides eight commands; “find,” 442 which performs afind for a specified object; “members,” 444 which permits certain usersto change the membership list and access levels associated with members;“create,” 446 which allows certain users to create new items and pages;“edit,” 448 which allows certain users to edit eRoom pages; “settings,”450 which permits settings for the display and management of eRooms tobe changed; a question mark icon 452 which invokes a help system; a“next unread” icon 454 which displays to the viewer an unread item orfile; and an up-arrow icon 456 which displays the “parent” of the eRoomcurrently being viewed, that is, it displays an eRoom page one logicallevel “up” from the currently viewed eRoom page.

The graphical element 406 is used to pictorially identify the viewedpage. The graphical element 406 may be a corporate logo or otherorganizational identifier. The graphical element 406 may be static (asdepicted in FIG. 4) or it may be a dynamic identifier such as a JAVAscript or ActiveX control.

The item box 408 collects and displays items associated with the projectrepresented by the page 402. In the embodiment shown in FIG. 4, the itembox 408 contains a folder of items 482, a notes file 486, a spreadsheetfile 488, and a word processing file 490, each of these being links toother eRoom pages or files. Other items which may be displayed in anitem box 408 are version organizers, discussion, links, and vote/pollpages which survey team membership on one or more issues. The item boxmay also include a facility for creating new items 492. The item box 408may also include icons which control how items are displayed in the itembox 408. In the embodiment shown in FIG. 4, three icons are provided: an“icon display” icon 494 (currently selected) which causes items to bedisplayed as large icons with identifying text underneath; a “listdisplay” icon 496 which causes items to be displayed as small icons withidentifying text to one side of the icon; and a “report display” iconwhich causes items to be displayed as a list. The displayed list may bealphabetized, ordered by size of item, ordered by creation date, orderedby modification data, or ordered by some other data field associatedwith each item.

Items in the item box may include a graphical indication that it, oritems contained within it, are unread. This may imply that the item hasbeen newly created, or the item may have been modified since the viewinguser last read it. In either event, the graphical indication signals theuser that the item should be read. In FIG. 4, the “Brainstorms” folder482 has an indication 484 that it is unread.

eRoom pages also may include a shortcut bar 410. The shortcut bar is alist of shortcuts which provide the viewer with a convenient way toaccess other eRoom pages. For example, in the embodiment shown in FIG.4, a shortcut to the directory of eRooms is provided, as well asshortcuts to the page currently viewed 414 and a shortcut 416 the folder482 displayed in the item box 408. The folder shortcut 416 includes agraphical indication that there are unread items in the folder 417. Theshortcut to the front page of the eRoom currently being viewed 414 alsoincludes a graphical indication that unread items exists in the page415. Shortcuts may be added to the shortcut bar by the viewing user. Inorder to read the unread items in the folder 482, the viewing user mayuse the shortcut 416 to access the contents of the “Brainstorms” folder482 and determine which items are unread or the user may simply click onthe “next unread” icon 454. The shortcut bar 410 may be provided as anActiveX control or as a JAVA applet or other means.

As noted above, users interact with eRooms by using Web browsers in atraditional manner. That is, users may traverse a hyperlink to access aneRoom, or users may directly enter a URL address into the browser.Regardless of the manner in which the URL address is accessed, thebrowser retrieves the HTML file in order to display it. However, if theURL address is an eRoom, the server of the file returns a file ofcontrol information, referred to as a “wrapper” file. The wrapper fileis an HTML file which contains, among other information, anidentification of the object to be displayed. The wrapper file deliversan object ID which is used by the client workstation 12′ to look up theobject in the local database 20 stored on the client workstation 12′.The local database 20 includes information about the object, includingwhich eRoom template to use and information regarding any “children” theobject may have (for example, items contained in the item box).

Generation, display, and management of eRooms is controlled by a “pagebuilder” application residing on the client workstation 12′. The pagebuilder application may be provided as specialized hardware or softwareoperating on a general-purpose machine. In some embodiments, the pagebuilder application may be provided as an Active X control or a COMobject.

Referring to FIG. 5, the first step that is taken by the page builderapplication is to retrieve the eRoom template indicated by the wrapperfile (step 502). An eRoom template is an HTML file having additionaleRoom-specific information embedded in it. The eRoom specificinformation is generally distinguished from HTML tags. For example,eRoom-specific information in an eRoom template may be surrounded by“<<” and “>>”. Any symbol or set of symbols may be used to distinguisheRoom-specific information so long as eRoom-specific information isdistinguishable from HTML tags.

eRoom information in a template includes sections controlling the pageitself, the controls on it, and the way the page's data is presented thepage is created or edited.

The Template section controls several miscellaneous items about thetemplate itself, for example, the Template Section may include nameinformation, information specifying which thumbnail appears when thepage template is selected, a description of the identifying text thatappears under the thumbnail, how children (i.e. dependent pages) of thistype of page are counted, and whether the page should open automaticallywhen created. In one embodiment, the Template section of a Folder may beconfigured in the following manner:

Begin_Template

{

category=container

wizardname=“Folder”

thumbnail=folder

Icon=0

DYNAMIC

{

Suffix=“item”

SuffixPl=“items”

OpenOnCreate=“no”

Blurb=“A container for storing and organizing files, links and otherpages.”

}

}

The template section above specifies the folder template's name(“Folder”), thumbnail, default icon, and identifying text (blurb).“OpenOnCreate” specifies that folders are not automatically opened whencreated, and “Suffix” and “SuffixP1” control the text that appears withthe child count in the size column when a folder appears in an item box.DYNAMIC sections allow the template creator to add properties to a pagethat are not standard template properties. For example, in the exampleabove, Suffix, SuffixP1, OpenOnCreate, and Blurb have been added to thistemplate by the template creator. The following is an exemplary list ofvarious template properties that may be used in embodiments of theirinvention:

Template Properties

Category: specifies which set of icons is presented when a “Change Icon”command is attempted on items with this template. Valid choices are“container” (for folders and version organizers), “content” (for notepages) and “discussion” (for discussions). Discussion notes do have acategory (“note”), but actually they never appear with icons.

Wizardname: specifies the name of the template when it appears as achoice in the page wizard. “Folder” and “Note” are examples of these.

Thumbnail: which thumbnail to display when this template is selected inthe page creation facility. Thumbnails may be .bmp files stored in apredefined subdirectory which refers to them by name without the .bmpextension.

Icon: the index number (within the icon set specified by “Category”) ofthe default icon for items with this template.

Suffix: the string to use after the child count in the size column whenitems with this template appear in the item box, e.g., “item” forfolders, “note” for discussion, “version” for version organizers. Thisproperty must be placed within the braces of a “DYNAMIC{ }” subsectionwithin the Template Section.

SuffixP1: the plural version of the Suffix. e.g., “items”, “notes”,“versions”.

OpenOnCreate: whether or not to open new items of this typeautomatically when created. “No” for folders, generally “Yes” foreverything else.

Blurb: the identifying text that appears under the thumbnail when thistemplate is selected in the page wizard.

The Control section(s) appear for each eRoom discussion or item box onthe page, setting various properties like the column headers of an itembox, or the sort-direction of a discussion. In one embodiment, theControl section for the item box in a Folder may be configured in thefollowing manner:

Begin_Control

{

controlname=ERPage

wizardname=“contents”

childtype=“container,discussion,content,external,link”

defaulttarget=yes

DYNAMIC

{

InitialView=“Report”

ShowCreation=FALSE

ShowModifyTme=True

ModifyWidth=116

SizeWidth=68

Width=443

}

}

The “DYNAMIC” section for the example above specifies that the item boxin a Folder starts displaying items in Report display, does not show acolumn for creation date, does show the time along with the date in theModified column, and has modified column widths. The following is anexemplary list of various control properties that may be used inembodiments of the invention.

Control Properties

controlname: the section to which the control applies.

childtype: which categories of templates may be created of this page.

defaulttarget: set if the template has an item box into which itemsdropped on the icon for this page should go.

excludechildcount: set on item boxes or discussion whose children ornotes should not count as part of the page's size, like the Attachmentsbox on a Note page, and the embedded discussion areas on folders andversion organizers.

substorage: set if creating one of these should also create its firstchild. Used for discussion, so that the page wizard for creating adiscussion also prompts the user to title and enter the first note.

InitialView: specifies the initial display mode of items on this page(Report, Small icon, Large icon). This property must be placed withinthe braces of a DYNAMIC { } subsection within the control template.

SwitchViews: allows the page to hide from a user the ability to switchmodes. This property must be placed within the braces of a DYNAMIC { }subsection within the control template.

CreateLabel: overrides “Create” as the creation button label. Thisproperty must be placed within the braces of a DYNAMIC { } subsectionwithin the control template.

TitleWidth: specifies the title column width. Otherwise, the titlecolumn will size itself dynamically to fill the space left by the othercolumns. This property must be placed within the braces of a DYNAMIC { }subsection within the control template.

CreateWidth, ModifyWidth, OwnerWidth, SizeWidth: used to specifyalternate column widths. This property must be placed within the bracesof a DYNAMIC { } subsection within the control template.

TitleName, CreateName, ModifyName, OwnerName, SizeName: used to override“Name”, “Created”, “Modified”, “Owner” and “Size” as the column names.This property must be placed within the braces of a DYNAMIC { }subsection within the control template.

ShowSize, ShowOwner, ShowModification, ShowCreation: allowing display orconcealment of these columns. This property must be placed within thebraces of a DYNAMIC { } subsection within the control template.

ShowCreateTime, ShowModifyTime: set to show time, along with date, inthese columns. This property must be placed within the braces of aDYNAMIC { } subsection within the control template.

ShowSizeSuffix: allows the size column just show a raw number, not “xnotes”, “x items”, etc. This property must be placed within the bracesof a DYNAMIC { } subsection within the control template.

SortColumn: set this to “Create”, “Modify”, “Owner”, or “Size” tospecify a column other than the name as the initial sort key.

SortAscending: specifies reverse or normal sort.

ShowHeader: set this to “False” to hide the column headers.

Width: set this to the width of the item box. This property is used tomake sure the icons for newly created items are given the correct XYcoordinates for Large Icon mode.

AnnotationTarget: set this to the name of an item box in the currenttemplate to make the Edit New Version command appear for items in thisitem box. The new copies will be sent to the item box specified.

The Wizard section: this section defines the functions used for creatingand editing the page. Each widget in the wizard is listed here, withproperties controlling what sort of widget it is (checkbox, plain textor rich text), the text of the prompt that appears before it, and thedefault value. The Wizard section in a Folder looks like this:

Begin_Wizard

{

Name

{

widgettype=text

prompt=“Name”

default=“”

indent=32

DYNAMIC

{

longdescription 32 “Choose a name for this

folder, and add a description of you want

one.”

}

}

Use Description

{

widgettype=checkbox

prompt=“Show description”

default=TRUE

}

Description

{

widgettype=rich_text

prompt=“”

default=“”

indent=0

DYNAMIC

{

richtextheight=153

}

{

UseComments

{

widgettype=checkbox

prompt=“&Include space for comments”

default=TRUE

}

}

The widget section described above specifies four editable widgets inthe wizard: a text box for the title, checkboxes for whether or not touse the description and the embedded discussion, and a rich-text box forthe optional description. The following is a list of wizard propertiesthat may be used in various embodiments of the invention.

Wizard Properties

Widgettype: which edit widget to use for the property. Can be “text”,rich-text” or “checkbox”.

Prompt: the text to show before the widget.

Default: the default value for the property

Indent: how much to indent the widget to the right of the prompt. Anindent of 0 means to put the widget below the prompt, not the right ofit.

Longdescription: This property must be placed within the braces of aDYNAMIC { } subsection within the control template. used on the firstwidget in the Wizard section, to provide an optional extra line ofinstructions to appear at the very top of the wizard page.

Richtextheight: used on rich-text widgets, to control their height. This

property must be placed within the braces of a DYNAMIC { } subsection

within the control template.

The header for many pages also includes an “INCLUDE” tag, which refersto additional header information for embedded discussions (see below),which is stored in a separate template for convenience.

Referring once again to FIG. 5, once the appropriate template has beenretrieved from mass storage associated with the client workstation (step502), the next step taken by the page builder application is to replaceall of the Replace Properties contained in the template with projectinformation from the project database (step 504). Following is a list ofexemplary Replace Properties:

Replace Properties

Name, Description, UseDescription, UseComments: editable properties fromthe page wizard.

$ROOM: the name of the eRoom.

$CREATOR: the creator of the eRoom.

$CREATEDATE: the date and time the eRoom was created. Allowable formatsare “short,” which displays some abbreviated form of the date such asdate-slash format or month-year format, and “long,” which displays thefull year including month year and day.

$ERDATADIR: the full path subdirectory in which eRoom data for the pageis stored.

$DISCUSSIONBODY: the body of a discussion.

$DISCUSSIONINDEX: the list of note titles used for the sidebar index indiscussions.

In order to fully render an eRoom the page builder application uses theportion of the project database which is stored locally on the clientworkstation 12′, as well as any files which are stored locally, to “fillin” any replace properties contained in the template. For example, ifthe page builder application encounters a $DISCUSSIONBODY replaceproperty, it accesses the local database 20 cells that contains thediscussion indicated by the replace tag and includes the text of thatdiscussion in the rendered eRoom page. The page builder application maybe written as a procedural routine that examines an eRoom template for aparticular set of replace properties; in this embodiment, the pagebuilder application would need to be rewritten whenever a new replaceproperty is defined.

Because multiple users may concurrently, and even simultaneously,perform work on a project, the page builder must ensure that the objectsfrom the local database and locally stored files are not stale beforeinserting them into the eRoom template (step 506). Put another way, theclient workstation's local project database 20′ must be synchronizedwith the server's project database 20 to ensure data coherency.Synchronization may be done in at least four different ways: (1)periodically in the foreground; (2) event-triggered in the foreground;(3) periodically in the background; and (4) event-triggered in thebackground. If synchronization is done in the foreground, then the useris blocked from performing any work while the synchronization occurs.Background synchronization allows the user to continue working. Forexample, the object ID for an object is used to query the local database20′. The object record may include a modification tag value (asdescribed above), or each data object may be provided with one or morestate bits which can be set to indicate the file or data is stale. Ifthe modification tag value or state bits indicate that the object needsto be synchronized, the updated object may be requested from the serverin the foreground or in the background. Alternatively, a clientworkstation 12′ may periodically search its entire local database 20′for objects which need to be updated. This may take the form of adatabase query for objects having a modification tag value less than thecurrent value, or a database query for objects having a particular valuefor state bit fields. Objects returned by the query are requested fromthe server as discussed above.

Synchronization is enabled by storing all records in the server databasewith an associated modification tag. The tag is a positive integer whichis taken from an ever-increasing counter. The counter increments eachtime it is read, i.e., each time a new modification tag is assigned to adata object stored on the server 14. When a client workstation 12′synchronizes its local databases and files, it also receives the currentmodification tag, i.e., it also receives the current value of thecounter. Alternatively, the current modification tag value can beincluded as extra information in each “wrapper page.” The clientworkstation 12′ includes the last modification tag value it receivedwhen it makes a subsequent synchronization request. The server 14transmits to the client workstation 12′ any data objects to which theuser has appropriate access rights that also have a modification tagvalue greater than the modification tag value sent with thesynchronization request. The client workstation 12 stores the receiveddata objects in its local database and stores the new receivedmodification tag value. Client workstations 12′ and servers 14 may beseparated by relatively slow, lossy channels such as telephone networks.Accordingly, synchronization requests can sometimes fail for variousreasons, e.g., a connection node is out of service or a necessarytransmission line suffers too many errors to allow a reliable connectionto be made. In this event, the synchronization request fails and shouldbe retried later.

Once synchronization has been accomplished and local database metadatahas been updated, the appropriate data objects and values are insertedinto the eRoom where indicated by Replace Properties, and the eRoom isdisplayed to the user (step 508) by the browser application in atraditional manner (refer to FIG. 4).

Files displayed by an eRoom may be viewed or edited by team membershaving the appropriate access controls (discussed in more detail below).A user indicates that a particular file should be retrieved from theserver for editing or viewing by any one of a number of traditionalmethods, such as double-clicking, selecting the file and pressing the“Enter” key on the keyboard, or pressing the right-hand key on a mouseinput device and selecting the appropriate action from the displayedpop-up menu. File download and subsequent upload, if necessary, ismanaged by a background daemon. Alternatively, file upload and downloadmay be managed by a separately executing program; the only requirementis that the file upload/download application executes separately fromthe browser application, so that premature exiting of the browserprogram is handled appropriately by upload/download code.

Referring now to FIG. 6, the first step taken by the background daemonis that the local file directory is checked to determine if the selectedfile is already resident in local mass storage associated with theclient workstation 12′ (step 602). If the file is not present or isstale, then it must be downloaded from the server 14. The file ischecked to determine whether another client workstation 12 has caused anedit lock to be set on the file indicating that the file is beingedited. This may take the form of a database query for the object IDassociated with the file which returns at least the metadata associatedwith the file indicating presence or absence of an edit lock. If no editlock has been set for a requested file, the access rights of therequesting user are checked. If the user has appropriate access rights,i.e., “can edit” if the user has indicated editing will occur or “canview” if the user has indicated only viewing will occur, the user willbe allowed to retrieve the file. In the case of a user that indicatedediting will occur, an edit lock is set before the file is downloaded.This ensures that no other user will be able to download the file forediting purposes while the edit lock is set. The requesting user isblocked from further work until the file download is complete. Filetransfers are accomplished using HTTP and this process is described inmore detail below.

Once the file has been downloaded, or if the file was already present inlocal mass storage, the Watcher launches the application used to editthe file (step 604). The indicated application may be determined usingthe Object Linking Embedding standard (OLE), the file suffix (threecharacters in a DOS-based system), or the server 14 may store filemetadata which is transmitted together with the file and indicates whichapplication should be used to open and edit the file. If the server 14stores file metadata, a list of alternate applications may be stored,either on the server 14 or the client workstation 12, so that if aclient workstation does not have access to a first application, otherapplications are specified which may be used.

The background daemon waits for the indicated application to exit, orthe document to close, before taking further action (step 606). Once theapplication has exited, the background daemon determines if the file hasbeen modified (step 508). If not, the background daemon does not need totake further action, except for freeing the edit lock if one was set.However, if the file was modified, then it must be uploaded to theserver 14 using HTTP (step 610). The file upload may be done in thebackground or in the foreground. If done in the foreground the user willbe blocked from further work on that file until the upload is complete.Once the upload is complete, the server 14 updates metadata stored inits database 20 that is associated with the file, for example, any editlock set by the editing user is released.

As noted above, users may perform work on files and objects locally andupload the modified files and objects to the server 14 for viewing,comment, or further modification by other project team members. Thesystems and method of the present invention allow users to upload newlycreated and modified files to a server 14 using an intuitivedrag-and-drop method.

Referring now to FIG. 7, a user creates a new file or modifies a filedownloaded from the server 14 (step 702). It should be understood thatthis step includes actions such as creating a new version of the filelocally so that other users may still check out the “original” copy ofthe file present on the server 14. Once the user is finished editing thefile, it may be uploaded to the server 14 to allow other users access toit. The user signals that the file should be transmitted to the server14 by dragging the file onto an eRoom displayed by the browser (step704). Dropping the file into the displayed eRoom invokes an ActiveXcontrol or a background daemon process which manages the upload of thefile to the server 14.

The user's access rights are checked to ensure that the user possesses“create” or “modification” rights for the page to which the user desiresto upload the file (step 706) and the file to be uploaded is stored tolocal mass storage (step 708). Access rights may be checked over thenetwork in many ways. For example, each object may be provided with afield or fields which identify users that may open, view, and edit theobject. Alternatively, an object may assign a pre-defined value to afield which controls access to the object. For example, a “coordinator”role may be defined and an object may identify that any coordinator mayedit, open or view it.

If the user has the appropriate rights, then a command is sent to theserver to create a new file (step 710). This step may be skipped if theuser is modifying a file instead of creating a new file. However,creation of a new file allows the server to provide a degree of faulttolerance and version control, if those features are desired. If theserver has been instructed to create a new file, a new object is createdcontaining metadata associated with the data file and the file istransmitted to the server 14 using HTTP (step 712). If a filemodification is occurring, the server 14 updates the metadata containedby the data object associated with the file and the file is transmittedto the server 14 using HTTP (step 712). The server 14 associates theuploaded file with the newly-created data object.

File metadata may include: the name of the file; the size of the file;the date the file was created; the date the file was last modified;access information such as which users may open, view, and edit thefile; and information regarding the edit status of the file, such aswhether an edit lock has been set by a user.

HTTP Transfer Protocol

Throughout the specification, whenever reference is made to transmittingdata to or from a client workstation 12′, the transfer is accomplishedusing HTTP. While this is the traditional way to transmit HTML filesfrom severs to clients, it is not used to transmit HTML files fromclients to servers. The systems and methods described herein use HTTP totransmit large files of data, such as word processing files,spreadsheets, etc. The advantage of using HTTP to transmit all projectdata is that users from different organizations can easily andtransparently share data since data transmitted by HTTP will be morecompatible with firewalls or other security mechanisms established bytheir respective organizations.

Referring now to FIG. 8, the first step in transmitting data using HTTPis that the client workstation 12′ obtains any proxy server settings inuse by the browser application executing on the client and stores thoseproxy settings for later use (step 802). The client workstationestablishes an authentication context by connecting to a server using aseries of HTTP commands (step 804). This is much like the process usedfor logging into a server 14 hosting eRooms, and is described in greaterdetail below. An authentication context may be any method forestablishing the identity of a remote user; a common context is ausername-password pair.

The client workstation 12′ establishes an HTTP connection to the server14 (step 806) using the proxy settings stored in step 802 and sends anHTTP POST request to the server 14. The HTTP POST request includes: aURL identifying a directory located on the server 14 where the datashould be stored; an identification code uniquely identifying the data;a header containing information about the data such as authorizationinformation; and the data itself.

Once the eRoom server 14 has verified the uploading user'sauthentication context, e.g., username and password pair, it receivesthe data and stores it based on the document identification codetransmitted in the HTTP POST command (step 808).

Access Control

As noted above, the eRoom skeleton is the set of database records thatcontain the basic properties needed to display an eroom. The concept ofskeleton information provides a first level of access control, becauseonly data objects stored in “containers” for which a particular user hasOpen privileges are synchronized to that client's workstation 12′.

Since every file and eRoom item is represented as an object in thedatabase, access of users to each item can be controlled by entries inthe database schema. For example, every eRoom may be represented by atable which has as one or more of its fields, a list of the members thatare entitled to enter the eRoom. In some embodiments, users may bedivided into three separate groups: coordinator; reader; andparticipant. In this embodiment, a coordinator can add members to theeRoom and may supersede any rights granted to users. A reader is someonewho has access to the eRoom solely to view the content of that eRoomwhile a participant is a user that may access the eRoom and may edit theobjects and files contained in the eRoom as well as upload new objectsand files to the eRoom. User access may be checked by running thedatabase query on the appropriate table and only allow a user to accessthe eRoom when that user's name or authentication context appear as anentry in the table, i.e., is returned from the database query as aresult.

Some embodiments, include a “persist layer” which provides persistentstorage to a relational database. The persist layer provides anapplication program interface which allows application programs to issueindividual commands to relational databases, each command providing aflexible number of input parameters and output return values. Eachpersist command may be mapped to a database query statement that is usedwhen the command is executed. This mapping is encapsulated, i.e., hiddenfrom clients of the persist layer. Encapsulation of the persist commandsallows them to be redirected to different databases or optimized withoutrequiring the client application program to be modified.

In another embodiment, the persist layer described above is based on theODBC protocol. ODBC allows an application program to “prepare” a dataquery and then execute the prepare statement multiple times. Executionof prepared statements offers significant performance improvements. The“persist layer” may further monitor which statements are executed mostoften. Based on statement execution counts, statements may bedynamically prepared based on their usage. In some embodiments, astatement may be prepared for a limited period of time, after which itis “unprepared.” Alternatively, a statement may be prepared after acertain number of uses and then be unprepared if it is not used within acertain period of time.

While the invention has been particularly shown and described withreference to specific preferred embodiments, it should be understood bythose skilled in the art that various changes in form and detail may bemade without departing from the spirit and scope of the invention asdefined by the appended claims.

What is claimed is:
 1. A method for generating a HyperText MarkupLanguage (HTML) page for display at a client computer in a networkenvironment, the method comprising the steps of: (a) receiving projectdata from a server computer at a client computer, wherein the projectdata is associated with a shared work project via a network connection;(b) storing the received project data in a client database; (c)retrieving an HTML file from a client memory element; and (d) processingthe stored project data in conjunction with the retrieved template fileto generate at the client computer an HTML page representing a portionof a collaborative workspace and enabling a user to perform work on theproject data.
 2. The method of claim 1 wherein step (b) comprisesstoring the received project data in a ODBC-compliant database.
 3. Themethod of claim 1 further comprising: determining from a modificationtag associated with the stored project data if the stored project datain the client database requires synchronization with a server database;if synchronization is required, requesting modified project data via thenetwork connection from the server database; and replacing the storedproject data with the modified data received via the network connectionfrom the server database.
 4. The method of claim 1 wherein step (b)further comprises storing in the client database the received projectdata together with a modification tag.
 5. The method of claim 1 whereinstep (c) further comprises retrieving a template file from the clientmemory element in response to receiving the project data.
 6. The methodof claim 1 further comprising the steps of: (e) requesting a file fromthe server computer; (f) invoking execution of an application capable ofviewing the file; (g) determining, upon termination of application, ifthe file was modified; (h) transmitting the modified file to the servercomputer; and (i) storing the modified file in a server computerdatabase in a manner such that the modifications to the modified filebecome available to other users of the collaborative workspace.
 7. Themethod of claim 6 wherein step (h) further comprises transmitting themodified file to the HTML server using only a HyperText TransferProtocol (HTTP).
 8. A system for allowing a plurality of users tocollaborate on a shared project using a HyterText Markup Language (HTML)file server, the system comprising: a project database stored on aserver computer, the project database comprising project data related toa shared project; a client database for storing a subset of the projectdata related to the shared project; a plurality of template files storedat a client computer; and a page builder for processing the storedsubset of the project data with one or more of the computer a pluralityof HTML pages representing a portion of a collaborative workspace, andfor enabling the user to perform work on the subset of the project data.9. The system of claim 8 wherein a HyperText Transfer Protocol (HTTP) isused for all communications between a client computer and the servercomputer.
 10. The system of claim 9 wherein data files are transferredbetween the client computer and the server computer using HTTP.
 11. Thesystem of claim 8 wherein modifications or additions made to the sharedproject are reflected in the client database.
 12. The system of claim 8wherein the client database and the project database are periodicallysynchronized.
 13. The system of claim 8 wherein the client database andthe project database are cynchronized upon the occurrence of an event.14. The system of claim 8 further comprising server file storage on theserver computer for storing files related to the shared project.
 15. Thesystem of claim 8 wherein the project data contained in the projectdatabase comprises access control information.
 16. The system of claim 8wherein the project data contained in the project database comprises alist of users allowed to access the project data.
 17. A system forallowing a plurality of users to collaborate on a shared project in anetwork environment using a server computer, the system comprising, aproject database stored on a server computer, the project databasecomprising project data related to a shared project, a client databasefor storing a subset of the project data related to the shared project,a plurality of template files stored on the client computer and adaptedfor being combined with the subset of the project data to render HTMLpages for display at a client computer, and a page builder executing onthe client computer for processing the subset of the project data fromthe client database with the template files stored on the clientcomputer to render on the client computer a plurality of HTML pages,representing a portion of a collaborative workspace, the HTML pagesenabling the user to perform work on the subset of the project data, fordisplay at the client computer.